[PRD] zendesk: new-platform proposal - #230
Open
asachs01 wants to merge 1 commit into
Open
Conversation
Per CONTRIBUTING.md's Tier 3 process, this is a proposal for the Zendesk plugin requested in #10 — not an implementation. Zendesk has zero existing infrastructure in this repo (no gateway vendor entry, no local MCP server, no plugin scaffold), which puts it squarely in the "new platform" tier requiring PRD + maintainer approval before build. Zendesk does ship its own official hosted MCP server (early access since summer 2026, OAuth-gated, per-tenant subdomain) rather than requiring a WYRE-built server — this PRD scopes the plugin to connect to that directly, mirroring how Stripe/Slack/HubSpot/PandaDoc already work in this repo. Deliberately does not name specific MCP tools: Zendesk's server was in early access with no live tools/list available to verify against, and guessing names from REST endpoints or third-party community servers is exactly the failure mode issue #178's corrective pass just spent a full pass fixing across 18 other plugins. Flagged as an explicit prerequisite in Success Criteria and Open Questions instead. Refs #10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why a PRD instead of a plugin
Issue #10 requests a Zendesk plugin. Per
CONTRIBUTING.md's Tier 3 process ("Building a plugin for a vendor we don't support yet? Submit a PRD first"), Zendesk needs a PRD before implementation — it has zero existing infrastructure in this repo (no gateway vendor entry, no local MCP server, no plugin scaffold).What I found
Zendesk ships its own official hosted MCP server (
https://<subdomain>.zendesk.com/api/mcp, OAuth-gated, in early access since summer 2026) — so this doesn't need a WYRE-builtzendesk-mcpserver, same pattern as Stripe/Slack/HubSpot/PandaDoc already in this repo.What this PRD deliberately does NOT do
Name specific MCP tool names. Zendesk's official server has no live
tools/listI could verify against, and several community Zendesk MCP servers exist on GitHub with different tool surfaces than the official one — guessing from those (or from REST endpoint names) would recreate exactly the tool-name-drift problem issue #178's corrective pass just spent a full pass fixing across 18 other plugins. Flagged as an explicit prerequisite in Success Criteria and Open Questions instead.Scoped to read/triage/lookup (tickets, orgs, users, help center, reference data) — write actions are explicitly out of scope for v1.
Refs #10
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.